Subject: AIW5 Reference SIG Agenda

From: "Ralph Case" <[email-masked]>
Date: Thu, 2 Jun 94 16:09:11 EDT

Greetings, Reference SIGgers!

I'm working on the agenda for the APPN Architecture
Reference SIG at the June AIW.  If you have any
questions or topics for discussion at the SIG, please
post them here or send them to me directly.

The agenda should reflect the common interests of the
members.  I try to gauge what those interests are based
on what I hear from you, so remember that your input
is important.

Here are some things to think about...
   - Have you come across any architecture that requires
     clarification that may be of interest to the other
     AIW members?
   - Have you discovered any holes in the APPN
     architecture that need to be addressed?
   - Do you have any proposals or submissions for
     enhancements to APPN architecture for the SIG to
     consider?

I look forward to hearing from you and talking with
you later this month.

Ralph Case                    [email-masked]    (919)254-1882
APPN Architecture
IBM Networking Hardware Division

---

From: Dario Calia <[email-masked]>
Date: Wed, 22 Jun 94 15:52:49 PDT

> Hello Ralph,
> 
> I put this letter together a few weeks ago, but did not get a chance to
> send it.  I would like to address the architecture changes which are
> floating around, but have not been documented yet.  
> 
> I have not attended the previous AIWs, but I have been able to peruse the
> publications from three previous AIWs.  From these I have abstracted what
> I thought were changes to the Architecture (-03).  I am attaching the list
> below.  Some are duplicates, some may not be changes.  What I would like is
> a list of all the architecture changes which are being incorporated? 
> That is, which items on the list below are not changes, are just clarifications,
> are changes, etc.  Some of the items below have been addressed already.
> 
> Ciao, Dario
> 
> p.s.- By the way, not all the changes currently on ibmstandards (networking?)
> contain an abstract.  Actually, they maybe included but they are pkzipped.  I
> currently don`t have a pkzip version for unix.  If someone has one could they
> forward it to me?  How about using unix tar and compress also?
> 
> Attachment:
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Summary of Modifications Made to the Architecture of Record (-03)
> 
> MISCELLANEOUS
> o	LAN address resolution services (9/23/93 AIW)
> o	CV x46, sub-vector x80 on SNA Format XID 3 included
>         when CN (9/23/93 AIW)
> o	No default NETID (2/17/94 AIW)
> 
> TRS
> o	Correcting Distributed TDB when NN becomes EN/LEN (2/17/94 AIW)
> o	Limit of one TDU per conversation (2/17/94 AIW)
> o	Strip off network identifier from TG partner when  
>         building RSCVs (2/17/94 AIW)
> o	NNs must not Increment own RSN during initial topology  
>         exchange (2/17/94 AIW)
> o	Negotiating FRSN in initial topology exchange w/ non  
>         safe store NNs (2/17/94 AIW)
> o	Receiving blank/null mode or COS names (2/17/94 AIW)
> o	Building/interpreting routes through VRNs (2/17/94 AIW)
> o	CV x46, sub-vector x83 border node interoperability (2/17/94 AIW)
> o	MSB format for CV x46, sub-vector x82 MAC address (2/17/94 AIW)
> o	TRS directed locate route computation changes
> o	TG and VRN weight determination (9/23/93 AIW)
> o	TRS Performance Optimizations (9/23/93 AIW)
> 	  a. Separation of local and network topology (9/23/93 AIW)
> 	  b. Route computation using network portion (9/23/93 AIW)
> 	  c. NNS(OLU) route computation between local
>              to LEN attached LUs. (9/23/93 AIW)
> 	  d. RSNs for local resources will not be incremented
>              during initial topology exchange (9/23/93 AIW)
> o	Topology Safe Store (9/23/93 AIW)
> 	  a. Garbage collection updates w/ odd RSNs and
>              new indicator (9/23/93 AIW)
> 	  b. Time To Live support (9/23/93 AIW)
> 
> ISR
> o	Handling of two stage pacing (2/17/94 AIW)
> 
> ASM
> o	Dependent LU Range unconditionally reserved (2/17/94 AIW)
> o	No bind rejection based on LFSID assignment (2/17/94 AIW)
> o	LFSID group allocation/management implementation
>         suggestion (2/17/94 AIW)
> 
> DS
> 
> o	Real partner CP name special handling (2/17/94 AIW)
> o	Incomplete and neutral replies from an EN (9/23/93 AIW) (2/17/94 AIW)
> o	Wildcard reply from an EN (2/17/94 AIW) 
> o	Prefer Explicit, non-surrogate replies over, etc.(2/17/94 AIW)
> o	Reply handling at NN(OLU), NN(DLU), and INN(2/17/94 AIW)
> o	Wildcard response handling from a directed locate (9/23/93 AIW)
> o	Directed locates and domain broadcast reply handling favoring
>         explicit non-surrogate replies (9/23/93 AIW DUP?)
> o	Surrogate owner bit setting (9/23/93 AIW)
> 
> SS
> o	CP-CP session awareness (6/21/93 AIW, 9/23/93 AIW)
> 	  a. Redefined interpretation of SNA XID Format 3 CP session
>              indicators (9/23/93 AIW)
> 	  b. New indicator in CP capabilities (byte 8 bit 17) (9/23/93 AIW)
> 	  c. Topology awareness (9/23/93 AIW)
> 	  d. Conwinner activation changes (9/23/93 AIW)
> 	  e. Operator commands to activate/de-activate CP-CP sessions
> o	RSCV `next hop` determination (9/23/93 AIW)
> o	Mode to COS Mapping clarifications (9/23/93 AIW)
> 
> NOF
> o	Parallel TG support over LAN, DEFINE_LINK_STATION with local SAP address(2/17/94 AIW)
> o	Operator command to activate/de-activate CP-CP sessions (CP-CP session awareness)
> 
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> End of Attachment:
> >